home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #14
/
Monster Media No. 14 (April 1996) (Monster Media, Inc.).ISO
/
bbs_door
/
newchat.zip
/
SYSOP.ZIP
/
SYSOP.DOC
< prev
Wrap
Text File
|
1996-01-21
|
26KB
|
502 lines
NEWCHAT Version 3.54 -- Program & Design by Richard Levasseur
Copyright (C) 1996
DISCLAIMER
The author has taken every precaution to insure that no harm
or damage will occur on computer systems operating this package.
Nevertheless, the author shall NOT be held liable for whatever
may happen on your computer system or to any computer systems
which connects to your own as a result of operating this package.
The user assumes full responsibility for the correct operation of
this software package, whether harm or damage results from software
error, hardware malfunction, or operator error. NO warranties are
offered, expressly stated or implied, including without limitation
or restriction any warranties of operation for a particular purpose
and/or merchantability. If you do not agree with this then do NOT
use this program.
LICENSE AGREEMENT
The DOOR program, support files, and documentation are
copyrighted products of the AUTHOR. The AUTHOR reserves all rights
to these products. This is protected by the United States of America
(USA) and International Copyright Laws. In no way shall the
components of the DOOR software package be reproduced
or modified in any form or method without prior expressly written
permission from the AUTHOR.
Tampering with or altering the contents or integrity of the Door
software package is prohibited. No fee may be charged by any
agency other than the AUTHOR beyond the cost of distributing
unregistered copies without prior expressly written permission from
the AUTHOR.
A major portion of this software was written by Scott Baker and
Steven Lorenz. Mr. Baker's Doordriver kit and the changes made
by Mr Lorenz have been used for the communications and interrupt
handling and this part of the software remains copyrighted by them.
This DOOR is distributed under the Shareware concept. You are
allowed to operate this DOOR for a trial period of thirty (30)
days. After this trial period, you must register the DOOR
or discontinue its usage. Again if you do not agree with this
then do NOT use this DOOR.
INTRODUCTION:
------------
Ok, This is new. I've seen many chat rooms on many sytems. The problem
I've always seen with most of them is they either require one user to
finish typing before the other can begin, or a user may ask another user
a question that they do not see the answer to until the reply is complete.
This creates a kinda game I call chat tag. One user is writting back,
while the other is writting "Hey where did you go..". Well, this helps.
One problem, and as of yet, incorrectable, ASCII users are in the dark.
The users must be using rip or ANSI terminals to use this chat.
My NEWCHAT will split in up to 4 simultaneous windows that all users can
type in at the same time. It includes action commands, and a way for the
sysop to configure some commands for adult access users. All the users
must have that level or higher to get these actions. It has taken over
8 months of work on this product. If you run more than 4 nodes, or just
three nodes and you join in locally, the 5th person who tries to join in
the chat room will be told the chat room is currently full. You may add
more rooms in other door options for more rooms. The only draw back is
only 4 people per room. But this is a much easier chat room to follow
as a user and people do enjoy it on my system. It has a TREK Style look
in ripterm, and has been tested with Rip 1.54 and 2.0+ It autodownloads
the missing icons, and will display the sysops photo at the end if one
is available. The JPG for Rip 2.0+ is named the last 8 letters of the
sysop's last name. Example: For my BBS, LEVASSEU.JPG. If one is not
available the NONE.JPG is sent. Rip 2.0 users even enjoy a sound clip
with thier CHAT. The sound is produced each time a user enters or leaves
the chat room. If a user is already in the chat, and someone else
is about to join, but is delayed by having to download the missing icons,
the user waiting is informed of this.
REQUIREMENTS:
------------
At this point in time the only requirements are FILES=10 (or more) in your
config.sys file. ANSI.SYS or DVANSI with SHARE must also be loaded.
YOU MUST ALSO BE RUNNING RAMDRIVE ON YOUR SYSTEM. A FOSSIL is NOT
required to run the Door, although one will be supported if it exists.
Automatic time slicing support is provided to most common multi-taskers as
well. And while a JPG loads, it shows the image in a special area on the
screen. Please read installation info. I currently have no trouble
running this on a 486DX-40 with two nodes and a local with 8 meg of mem.
Files Included
--------------
Below is a listing of all files for the this Door. If you are
missing ANY of these files (except for the DOC and FRM files), the Door
will NOT function. Feel free to give out copies of the ENTIRE archive
package of this Door but please make sure all the files below are in that
package:
SYSOP.ZIP - This documentation with all the other
docs. for registration and installation.
NEWCHAT.EXE - Main Executable Door File
CHATSET.EXE - Set up program to create the required
NEWCHAT.CTL file. Answer all the questions.
Just type VARSET for help. If you want
to edit an existing CTL then type its name
after VARSET.
NEWCHAT.CTL - WARNING - THIS FILE MUST BE ALTERED TO YOUR
SYSTEM. It is the control file.
RUN VARSET for OPTIONS!
UPLOAD1.BAT - UPLOAD2.BAT - Example of BAT files used to implement
external transfers from two different nodes.
Using DSZ.EXE, DSZ.COM or GSZ.COM will give
you the download YMODEM ability. The number
after the upload filename is the node number.
*YMODEM WAS USED TO STOP RIP 1.54 FROM
USING RECOVERY ZMODEM WHILE SENDING SAME
NAME FILES. SEE UPLOAD BATCH FILES FOR USE
WITH GSZ, WORKS WITH DSZ TOO.
ACTIONS.DAT - List of Available Actions in the chat.
Formated like this..
00 - Level
Menu Item
Phrase to say with %1 to place a name.
NAME.ANS <-Name of ANSI to show with two
nodes.
See Example..
< INCLUDED ANSI FILES MAY BE CHANGED >
BEBACK.ANS FRENCH.ANS HUG.ANS NUDGE.ANS
FINGER.ANS FROWN.ANS HUH!.ANS PUNCH.ANS
ROSE.ANS SMILE.ANS
< INCLUDED ANSI FILES DO NOT CHANGE >
INCOMING.ANS NOROOM.CLR PAGE.ANS
PAGE2.ANS TIME.CLR
COMM_OFF.WAV - WAV played when a user leaves chat.
COMM_ON.WAV - WAV played when a uesr joins chat.
COMCODE.WAV - WAV played when first entering chat.
DCEARTH.ICN - ICN shown when leaving chatroom. RIP 1.54
NONE.JPG - JPG shown when the sysop photo is not
available at end.
UFPII.ICN - Icon shown on welcome to chat for Rip 1.54
UFPII.BMP - Icon shown on welcome to chat for Rip 2.0+
WHOSON.EXE - Special Free Pogram for USE by Spitfire BBS
Operators. Will change the appearance of
the (W)ho's on node option to users.
If placed in the Batch to run the chat,
other users will be told that another user
on the other node is "IN NODE CHAT".
RUN WHOSON.EXE to see options. Place in
Spitfire's work directory.
Files created by the Door when errors are encountered:
ERROR.LOG - Log of system errors which happen during Door play.
Installation
------------
--> NOTE: The word "Door" is used in place of the program name for
both the executable file (example Door.EXE), and the CTL
file (Example Door.CTL) in the documentation from this
point on. DoorDIR is used in place of the program directory
in the documentation from this point on.
--> UPGRADE: Once you register the codes given will work with any new
version that may come out.
1. Create a directory for the Door (example: "WC30\DOORS\DoorDIR")
2. Make sure that ALL files listed above from the Door package
are moved into that directory.
3. Use chatset.exe newchat.CTL.
4. Answer all the questions correctly.
5. To insure proper multi-node use DOS SHARE must be loaded prior to
the Door and prior to DESQview. And create a RAMDRIVE. See DOS
book, or use HELP RAMDRIVE for 6.0+ users.
6. In order to run the Door program online the following parameters may
be used.
"/Bxxxxx" This tells Door.EXE to lock its baud rate at
xxxxx. In order to get the most efficiency out of a high speed
error correcting modem (9600 baud or above), you may lock the baud
rate to a speed higher than what the caller is actually using.
By locking the baud to say 38,400, the modem can compress text data
that is being sent and achieve a baud rate much higher than the
actual transmission rate.
This will lock the baud rate at the same value for all nodes that
use this command line. If you perfer a more selective way to lock
baud use 'LOCKBAUD' command in the Door.CTL file.
"/Cx" (where x is 1..4) This specifies a comport number.
Some bbs software does not create door information files (dropfiles)
that contain the comport number. If your bbs does have a comport
listed in the dropfile then there is no need for this parameter.
The default is comport 0, local mode.
"/E" - Expanded Memory Specification If your machine has over one
megabyte of memory, then you may have some available. Door.EXE can
utilize EMS to improve Door performance and reduce conventional
memory requirements.
This command will tell Door.EXE to use EMS memory to hold its
overlay buffer. Otherwise disc area may be used to hold this buffer.
This needs a memory manager and when enabled and is compatible with
DESQview.
"/L" This tells Door.EXE to load up in LOCAL mode.
This is good for testing or when a sysop just wants to "try out" the
door without messing with his BBS setup. The "/L" mode will ask the
user for his name and run the door in local mode.
"/Nx" (where x is 1..9) This specifies a "node number".
Some bbs software support multinode environments in which you must
know the node number of the drop file to use. For example, RBBS-PC
uses DORINFOx.DEF. If you specified "/N2" then Door.EXE would use
DORINFO2.DEF.
"/Mx" (where x is up to 2 filename acceptable characters)
Used to specify one of Multiple control files. If you have created
more than one Door.CTL file (Door1.CTL, Door2.CTL, etc.) for each
node or network PC then you can select the one you want by using
the /M parm.
Example: "/M2" will force Door.EXE to use Door2.ctl.
"/Pyyy" This specifies the path to the drop files.
For example, "/PC:\WILDCAT\WCWORK\NODE1" would tell Door.EXE to
look for the drop file in C:\WILDCAT\WCWORK\NODE1. If this is left
out the program assumes the drop file is local.
"/V" This command will tell Door.EXE not to show any display
on the local screen. Only a colored screen and a message will be
displayed. The cursor will not move as it will be turned off.
Saves a little processing on multi-tasking systems.
"/W" This flags the program that a network is present even
though no multitaskers are detected. This is useful if the door is
run on a network such as Novell that doesn't use multitaskers.
COMMON ERRORS
003 File path not found. Check to make sure the Door directory is
correctly named as DoorDIR.
201 Files not found. Check to make sure that all required Doors
files are in the DoorDIR directory.
7. Install the door into your BBS software (see your BBS software
documentation for more information). A batch file is normally
used to do this. To run the program just have your batch file
change to the DoorDIR directory and run Door.EXE - Thats all there
is to it! For dorinfo systems use the following:
Sample Batch File Entry
-----------------------
For node 1 running on Spitfire with extra free file..
CD\SF\WORK
WHOSON 1 N
NEWCHAT /N1 /Pc:\sf
CD \SF
9. Surprise! There is NO daily maintenance to be performed.
RESTRICTIONS ON THE UNREGISTERED Door
-------------------------------------
Until the Door is registered the following restrictions are in effect:
a. The users only be allowed to chat for 10 mins at a time..
b. And the users will only be allowed to use one action command per
chat sesion. .
c. All of the above will no longer be in effect once registered.
d. Once you are registered any future updates can be obtained free
through my BBS and my upgrades are ALWAYS easy to implement!
e. I am always improving my Doors - so check my BBS for a more current
version. Galaxy Class BBS (207) 582-8392 two nodes! They Hunt for
the free line. 14.4 on both currently.
WHAT TO DO IF THERE ARE PROBLEMS
--------------------------------
Every effort is made to ensure that the Door runs correctly before it leaves
my BBS as Shareware. If you are experiencing problems please do the
following BEFORE calling me:
Read ALL the SYSOP.DOC to ensure you have setup the program
and have met all the program requirements.
Multinode use
-------------
This Door supports multinode use and provides automatic multi-tasker
support (time slice releasing) for a wide variety of multi-taskers.
Common Problems (Locked Bauds, High Speed modems, etc)
------------------------------------------------------
1. The Door does NOT require a fossil driver to run.
2. If you are running a high speed modem (9600 baud or above), then I
suggest you run your bbs/mailer/doors at a locked baud rate. On high
speed error correcting modems, locking the baud rate will have a
noticeable increase on the speed of text that is sent. It's beyond
the scope of this document to discuss configuring your BBS and
mailer for a locked baud rate; you may wish to consult those docs
for information on that. Here are a few things to keep in mind when
setting up Door with a locked baud rate:
a. When using a locked baud rate, I highly recommend using a FOSSIL
driver. This Door will work at high speeds without one though.
BNU is a good fossil driver which can even be loaded and unloaded
before and after you run this Door.
b. If you are using a fossil, then make sure to tell the fossil
that the port is locked. For BNU, to lock com1: at 38,400, you
would use something like "L0=38400" on BNU's command line.
c. If you lock the baud for one program, it must be locked
for everything. You can't lock the baud for just this Door, but
not your BBS/mailer.
d. You may need to use the /B switch on the Door.exe Command line
to specify the locked baud rate. For 19,200 this would be "/B19200"
and for 38,400 this would be "/B38400". Please note there is no
space between the "/B" and the baud rate.
3. What follows is some information on possible strange situations
that may occur:
a. Low speed users can play the Door, but high speed users get
garbage.
- If you are not using the DORINFOx.DEF or DOOR.SYS drop file
then you may wish to find a converter program to convert
whatever drop file your BBS produces to the DORINFOx.DEF
or DOOR.SYS format and tell Door.exe to use that.
Several converter programs are readily available on most
BBS systems. CallDoor is a good one if you can find it.
b. The Door hangs up when a user enters the Door.
- Sounds like the Door is getting the wrong baud rate somehow.
Try switching over to the DOOR.SYS drop file method
if possible.
c. Text and screens are getting cut off.
- If you are running with a locked baud, then this could
be caused by some sort of FLOW CONTROL problem. Try using
a fossil if you aren't already.
d. If you're using something other than the DOOR.SYS drop file,
then I always suggest trying to use DOOR.SYS if possible. It is
the most reliable method and has had the most testing. If that
is not possible try DORINFOx.DEF as an alternative.
e. A door locks up node 1. This can happen with fossils or the
internal communications routines because it uses the default
comport of 1 when NONE is found in the dropfile or Door.ctl
file. To correct this make sure the right port is shown in
the dropfile OR Door.ctl file.
f. ANSI is reflected correctly on the local screen but the user
is getting garbage. Assuming the user has ANSI installed then
most likely the problem is at your end. First make sure you
have configured the Door.ctl file to show the correct locked
port rate. Second make sure the dropfile is passing the locked
port rate INSTEAD of the actual conncet rate. If it is not
passing the locked port rate then you may need to use a
different dropfile format OR use a dropfile converter program
to change the line to show the locked port rate INSTEAD of
the actual connect rate.
CREDITS:
--------
This relatively small section is just to recognize the GOOD people
who have made the DDPLUS based Door a possibility.
Shirley Robbins -=*=- I could not have accomplished this without
you. Your patience and care has made the hours
I've spent on this easier. You have shown me
great love, and stood by me while I fought this
endeavor. Most Girlfriends or wives would
have complained or left because of all the
time I was spending not being there to do
other things. THANKS YOU so much. You,
Shirley, are the most important part of my
life. I'm glad you didn't forget.
Scott Baker -=*=- The authors of the original DoorDriver Kit
and are to be thanked for releasing the
Derrick Parkhurst source code to their great kit! Without
that act of kindness DDPLUS would NOT
be possible and neither would this Door.
Scott is the author of several door Doors,
most notably Land of Devastation,
which uses the original doordriver kit.
Steven Lorenz -=*=- The author of the enhanced add on package
to Scott Bakers DoorDriver Kit. Thanks to
his code modifications, add ons and enhancements
DDPLus is a much more complete and capable
package then originally released in the
DoorDriver Kit.
Steve is the author of several door Doors, most
notably Railroad Empires, Romans At War, and
Empires at War, all of which use DDPlus.
Bob Dalton -=*=- The author of most of the DDPLus documentation
and contributor of the MISC.PAS and INITOVER.PAS
units used in the Door. Bob is the author of
several door Doors, such as GodFather of Crime,
Rise To Power, Task Force Broadside, Ship of the
Line, Grunt Fest, Way Freight and the Adventure
Door Door Toolkit, all of which use DDPLus.
DESQview is a registered trademark of Quarterdeck Office Systems.
Ripscript & Ripterm are registered trademarks of TeleGrafix Communications.
Spitfire was created and owned by Mike Woltz.
Where to reach me
-----------------
I can usually be reached at my BBS system, which should be listed in the
section entitled "registration" which is below.
Registration
------------
If you or your users enjoy this Door, then please register it.
Registration is $10.00 and you get a REGISTRATION code by mail or
posted on my BBS which will disable the UNREGISTERD portions, and
entitle you to life time support through my BBS. BBS Support
includes unlimited free updates and upgrades (not like some door
Door authors who charge for major upgrades/updates!) through my
BBS and access to the Door support conference on my BBS.
To register this Door just print out the registration form
(REGISTER.FRM) file included with the Door and send it with your
check or money order for $10.00 to:
Richard LeVasseur
127 Brunswick Ave. Apt #3
Gardiner, ME 04345
HOW TO REACH ME BY MODEM
---------------------------
Galaxy Class BBS (USA)
(207) 582-8392 (2400 to 14400 baud)
Two nodes! The open Node will Answer
Reminder: You will be mailed a LETTER with your registration code.
Just allow an appropriate amount of time (a week or two) after dropping your
check in the mail for it to arrive to me and the code to be sent by mail
back to you. If you need it sooner log onto my BBS, leave me a message
telling me you mailed the registration and when I receive your check or
money order I will post a private message on the BBS giving you the key
code. If you do it this way please allow at least a week from the time
you mail it to the time you call and get your code. If you go the BBS
route you will ALSO receive a key code by mail. REMINDER: No disks are
sent, if you need the most current version you must call my BBS for it.
Your code will work on all future updates to this package!
Bug Reports/Comments/Suggestions
--------------------------------
I have made every attempt to make sure the Door is free of bugs, BUT the
possibility always exists that one may have been missed by me or the
playtesters. If you find a bug, or have a suggestion or comment to make
leave a message on my BBS or Write to me. Please be very clear about what
happened. what system you are using ect..
Thanks for using my DOOR.
-Rich